Add expo plugin by ceopaludetto · Pull Request #1271 · callstack/repack

ceopaludetto · 2025-08-23T20:28:52Z

Summary

Add an expo plugin that allows expo router + expo CNG (expo managed projects) to work with repack.
Add a new guide to Expo

Test plan

Added a new expo managed tester application

Todos

Test Webpack Integration

changeset-bot · 2025-08-23T20:28:55Z

🦋 Changeset detected

Latest commit: 7341e40

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@callstack/repack-plugin-expo	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

vercel · 2025-08-23T20:28:57Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
repack-website	Ready	Preview	Comment	Sep 1, 2025 3:42pm

jbroma · 2025-08-26T19:59:26Z

Test plan

Maybe we should create an expo managed example in ./apps folder

Hey @ceopaludetto, absolutely, go for it 👍

ceopaludetto · 2025-08-29T19:41:48Z

@jbroma added a new expo guide in the docs and also added the tester application. We can combine both expo-modules and expo guides in just one page. Maybe we can also merge both plugins in just one, its up to you!

j0nl1 · 2025-09-01T12:41:05Z

I'm tracking the progress in this PR, very interested on it. I just wondering if would be possible to launch just with expo instead of react-native cli since it wouldn't require to manage pods locally or any kind of build just fetching a development build from expo cloud and run it using the repack bundler.

ceopaludetto · 2025-09-01T15:55:02Z

I'm tracking the progress in this PR, very interested on it. I just wondering if would be possible to launch just with expo instead of react-native cli since it wouldn't require to manage pods locally or any kind of build just fetching a development build from expo cloud and run it using the repack bundler.

Hey, thanks for the interest! The main reason we switched from expo CLI to React Native CLI is that when you run something like expo run ios --mode Release expo always builds the metro bundle before the native build (you'd need a patch to avoid this). Expo CLI works fine for development though (just use expo run ios --no-bundler to skip Metro).
As for expo cloud, I haven't really played around with that feature much, so I can't say for sure how it would work with this setup. If you end up experimenting with it, would love to hear how it goes!

jbroma

hey @ceopaludetto sorry for the delay with the review! I found few things we need to address but the rest looks good 👍

one more thing: when doing prebuild + run-ios I kept running into issues because I don't have cocoapods globally installed and use local ruby setup - perhaps we could fix that with Gemfile + Gemfile.lock like in other testers? (or maybe there is a nicer fix for that). Prebuild + android worked fine for me, good job with the tester 👍

jbroma · 2025-08-26T20:01:15Z

packages/plugin-expo/package.json

+    "node": ">=18"
+  },
+  "peerDependencies": {
+    "@callstack/repack": "workspace:*",


lets define those explicitly as a starting point for this plugin 👍

from my experience its best to define versions with open upper boundary, like >=53.0.0

jbroma · 2025-09-10T17:53:18Z

apps/tester-expo-app/app.json

Ran into some issues here when building Android, I think we are missing from fields like in the other tester app

jbroma · 2025-09-10T17:54:08Z

apps/tester-expo-app/index.js

shouldn't we use registerRootComponent from expo here?

jbroma · 2025-09-10T17:55:38Z

apps/tester-expo-app/rspack.config.mjs

+      // Alias both react and react-native to ensure that we don't end up with multiple versions
+      // of these libraries in the bundle.
+      //
+      // This is needed in these monorepo setups where there are multiple copies of react
+      // and react-native in the node_modules.
+      react: require.resolve('react'),
+      'react-native': require.resolve('react-native'),


is this an issue here with pnpm? Sounds like this should happen in setups with hoisting 🤔

jbroma · 2025-09-10T17:56:09Z

apps/tester-expo-app/rspack.config.mjs

+  },
+  module: {
+    rules: [
+      ...Repack.getJsTransformRules(),


lets use babel-swc-loader here instead (take a look at config for other tester)

jbroma · 2025-09-10T20:30:17Z

packages/plugin-expo/src/plugin.ts

+    new compiler.webpack.DefinePlugin({
+      'process.env.EXPO_PROJECT_ROOT': JSON.stringify(root),
+      // If Expo Router is enabled, pass additional environment variables
+      ...(router
+        ? {
+            'process.env.EXPO_BASE_URL': JSON.stringify(router.baseUrl),
+            'process.env.EXPO_ROUTER_ABS_APP_ROOT': JSON.stringify(router.root),
+            'process.env.EXPO_ROUTER_APP_ROOT': JSON.stringify(router.root),
+            'process.env.EXPO_ROUTER_IMPORT_MODE': JSON.stringify('sync'),
+          }
+        : {}),
+    }).apply(compiler);


I think its cleaner to split it into two DefinePlugin

jbroma · 2025-09-10T20:41:06Z

packages/plugin-expo/src/plugin.ts

+    if (
+      compiler.options.mode === 'development' &&
+      !!compiler.options.devServer
+    ) {
+      compiler.options.devServer.proxy ??= [];
+
+      // Redirect `/.expo/.virtual-metro-entry` to `/index` to match metro behavior in Expo managed projects
+      compiler.options.devServer.proxy.push({
+        context: ['/.expo/.virtual-metro-entry'],
+        pathRewrite: { '^/.expo/.virtual-metro-entry': '/index' },
+      });
+    }


this has no effect because devServer options are set before plugin apply runs - there is no way to inject devServer options through the plugin.

An alternative to that would be to wrap the entire user configuration and inject it there, kinda like Rozenite does it here

Rnbsov · 2025-11-23T18:06:57Z

waiting for merge sooooo much!!!!!!!

woals4815 · 2025-11-25T05:41:58Z

waiting for merge sooooo much!!!!!!!

@Rnbsov me either!!!!!!

vercel bot deployed to Preview August 23, 2025 20:30 View deployment

ceopaludetto force-pushed the feat/expo-plugin branch from 5d4d03b to 140d71f Compare August 23, 2025 20:36

vercel bot deployed to Preview August 23, 2025 20:36 View deployment

ceopaludetto force-pushed the feat/expo-plugin branch from 140d71f to 216ab15 Compare August 23, 2025 20:36

vercel bot deployed to Preview August 23, 2025 20:37 View deployment

vercel bot deployed to Preview August 29, 2025 16:54 View deployment

ceopaludetto force-pushed the feat/expo-plugin branch from 38e49a2 to f5bc4ef Compare August 29, 2025 16:56

vercel bot deployed to Preview August 29, 2025 16:56 View deployment

ceopaludetto force-pushed the feat/expo-plugin branch from f5bc4ef to d28352d Compare August 29, 2025 19:27

vercel bot deployed to Preview August 29, 2025 19:27 View deployment

ceopaludetto marked this pull request as ready for review August 29, 2025 19:28

ceopaludetto force-pushed the feat/expo-plugin branch from d28352d to 674306a Compare August 29, 2025 19:31

vercel bot deployed to Preview August 29, 2025 19:32 View deployment

feat: add expo plugin

2847e11

ceopaludetto force-pushed the feat/expo-plugin branch from 674306a to 07e0c75 Compare August 29, 2025 19:32

vercel bot deployed to Preview August 29, 2025 19:34 View deployment

ceopaludetto added 2 commits August 29, 2025 16:35

feat: add expo managed tester app

df9e533

docs: add expo guide

417fa62

ceopaludetto force-pushed the feat/expo-plugin branch from 07e0c75 to 1af629c Compare August 29, 2025 19:35

vercel bot had a problem deploying to Preview August 29, 2025 19:36 Failure

fix: lock file merge conflicts

7341e40

ceopaludetto force-pushed the feat/expo-plugin branch from 1af629c to 7341e40 Compare September 1, 2025 15:41

vercel bot deployed to Preview September 1, 2025 15:42 View deployment

jbroma requested changes Sep 10, 2025

View reviewed changes

dannyhw mentioned this pull request Dec 4, 2025

Whats the status of nativewind support #1312

Closed

Conversation

ceopaludetto commented Aug 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Test plan

Todos

Uh oh!

changeset-bot bot commented Aug 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🦋 Changeset detected

Uh oh!

vercel bot commented Aug 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jbroma commented Aug 26, 2025

Test plan

Uh oh!

ceopaludetto commented Aug 29, 2025

Uh oh!

j0nl1 commented Sep 1, 2025

Uh oh!

ceopaludetto commented Sep 1, 2025

Uh oh!

jbroma left a comment

Choose a reason for hiding this comment

Uh oh!

jbroma Aug 26, 2025

Choose a reason for hiding this comment

Uh oh!

jbroma Sep 10, 2025

Choose a reason for hiding this comment

Uh oh!

jbroma Sep 10, 2025

Choose a reason for hiding this comment

Uh oh!

jbroma Sep 10, 2025

Choose a reason for hiding this comment

Uh oh!

jbroma Sep 10, 2025

Choose a reason for hiding this comment

Uh oh!

jbroma Sep 10, 2025

Choose a reason for hiding this comment

Uh oh!

jbroma Sep 10, 2025

Choose a reason for hiding this comment

Uh oh!

Rnbsov commented Nov 23, 2025

Uh oh!

woals4815 commented Nov 25, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

ceopaludetto commented Aug 23, 2025 •

edited

Loading

changeset-bot bot commented Aug 23, 2025 •

edited

Loading

vercel bot commented Aug 23, 2025 •

edited

Loading